Skip to content

chore(deps-dev): bump @metamask/auto-changelog from 3.4.4 to 5.1.0 #382

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps-dev): bump @metamask/auto-changelog from 3.4.4 to 5.1.0 #382

wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 22, 2025 •
edited
Loading

Bumps @metamask/auto-changelog from 3.4.4 to 5.1.0.

Release notes

Sourced from @​metamask/auto-changelog's releases.

5.1.0

Added

  • Add --useChangelogEntry to auto-changelog update (#247)
    • This will read the PR referenced in each commit message, look for CHANGELOG entry: in the PR description, and use this as the new changelog entry in the changelog (or skip if the no-changelog label is present on the PR)
    • Note that GITHUB_TOKEN must be set in order to use this option
    • The updateChangelog function also supports this option
  • Add --useShortPrLink to auto-changelog update (#247)
    • This will generate short references to PRs, e.g. [#123](https://github.com/MetaMask/auto-changelog/issues/123) instead of [#123](https://some/repo)
    • The updateChangelog function also supports this option

Changed

  • Update auto-changelog update --autoCategorize to exclude entries with certain phrases or Conventional Commit prefixes (#247)
    • If commit messages have the following prefixes they will not be automatically added to the changelog:
      • style
      • refactor
      • test
      • build
      • ci
      • release
    • If commit messages have the following phrases they will not be automatically added to the changelog:
      • Bump main version to
      • changelog
      • cherry-pick
      • cp-
      • e2e
      • flaky test
      • INFRA-
      • merge
      • New Crowdin translations

5.0.2

Fixed

  • Fix --autoCategorize so that commit messages with Conventional Commit prefixes are categorized correctly when the prefix contains a scope (e.g. feat(scope): ...) (#240)

5.0.1

Fixed

  • Fix CLI path (#235)

5.0.0

Added

  • JavaScript sources and TypeScript declarations are now available in both CommonJS- and ESM-compatible variants (#226)
  • Add option to changelog validation to ensure that each entry in the changelog links to one or more originating PRs (#222)
    • Pass --pr-links to the CLI, or pass ensureValidPrLinksPresent to validateChangelog to enable this behavior, ideally in your lint package script or CI workflow
  • Add an optional shouldExtractPrLinks option to parseChangelog (#222)
    • When true, this will extract pull request links from the text of each entry, identify the pull numbers, and keep them in a separate array
    • See note on Changelog.getReleaseChanges below for more

Changed

  • BREAKING: Changelog.getReleaseChanges now returns an object whose values are objects of shape { description: string; prNumbers: string[] } rather than simply string (the description) (#222)
    • This affects parseChangelog as well, since it returns an instance of Changelog

... (truncated)

Changelog

Sourced from @​metamask/auto-changelog's changelog.

[5.1.0]

Added

  • Add --useChangelogEntry to auto-changelog update (#247)
    • This will read the PR referenced in each commit message, look for CHANGELOG entry: in the PR description, and use this as the new changelog entry in the changelog (or skip if the no-changelog label is present on the PR)
    • Note that GITHUB_TOKEN must be set in order to use this option
    • The updateChangelog function also supports this option
  • Add --useShortPrLink to auto-changelog update (#247)
    • This will generate short references to PRs, e.g. [#123](https://github.com/MetaMask/auto-changelog/issues/123) instead of [#123](https://some/repo)
    • The updateChangelog function also supports this option

Changed

  • Update auto-changelog update --autoCategorize to exclude entries with certain phrases or Conventional Commit prefixes (#247)
    • If commit messages have the following prefixes they will not be automatically added to the changelog:
      • style
      • refactor
      • test
      • build
      • ci
      • release
    • If commit messages have the following phrases they will not be automatically added to the changelog:
      • Bump main version to
      • changelog
      • cherry-pick
      • cp-
      • e2e
      • flaky test
      • INFRA-
      • merge
      • New Crowdin translations

[5.0.2]

Fixed

  • Fix --autoCategorize so that commit messages with Conventional Commit prefixes are categorized correctly when the prefix contains a scope (e.g. feat(scope): ...) (#240)

[5.0.1]

Fixed

  • Fix CLI path (#235)

[5.0.0]

Added

  • JavaScript sources and TypeScript declarations are now available in both CommonJS- and ESM-compatible variants (#226)
  • Add option to changelog validation to ensure that each entry in the changelog links to one or more originating PRs (#222)

... (truncated)

Commits

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot
chore(deps-dev): bump @metamask/auto-changelog from 3.4.4 to 5.1.0
63031c7 
Bumps [@metamask/auto-changelog](https://github.com/MetaMask/auto-changelog) from 3.4.4 to 5.1.0.
- [Release notes](https://github.com/MetaMask/auto-changelog/releases)
- [Changelog](https://github.com/MetaMask/auto-changelog/blob/main/CHANGELOG.md)
- [Commits](MetaMask/auto-changelog@v3.4.4...v5.1.0)

---
updated-dependencies:
- dependency-name: "@metamask/auto-changelog"
  dependency-version: 5.1.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 22, 2025
@dependabot dependabot bot requested a review from a team as a code owner September 22, 2025 12:13
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 22, 2025
@dependabot dependabot bot mentioned this pull request Sep 22, 2025
Closed
@socket-security
Copy link

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Block Medium
@octokit/[email protected] has Network access.

Module: globalThis["fetch"]

Location: Package overview

From: ? → npm/@octokit/[email protected]

ℹ Read more on: This package | This alert | What is network access?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@octokit/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Medium
[email protected] has Network access.

Module: globalThis["fetch"]

Location: Package overview

From: ? → npm/[email protected]

ℹ Read more on: This package | This alert | What is network access?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
[email protected] is a AI-detected potential code anomaly.

Notes: No definitive malware detected in this fragment. The main security concern is supply-chain risk from dynamically loading plugins from potentially untrusted sources. To mitigate, enforce strict plugin provenance, disable remote plugin loading, verify plugin integrity, and apply least-privilege execution for plugins.

Confidence: 1.00

Severity: 0.60

From: ? → npm/[email protected]

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant